do not specify anti-aliasing #8689

jtnord · 2023-11-10T19:48:25Z

specifying the anti-aliasing implies we know better than the browser (we don't). Specifiying this globally prevents the use of sub-pixel anti-aliasing where it is available and the browsers text rendering engines are these days pretty much fantastic that they should not need these hacks.

and for good measure - here is an article from 10 years ago https://usabilitypost.com/2012/11/05/stop-fixing-font-smoothing/ and the mozilla doc saying do not use it on a public facing web site. https://developer.mozilla.org/en-US/docs/Web/CSS/font-smooth

See JENKINS-XXXXX.

Testing done

Proposed changelog entries

Tweak font styling to remove anti-aliasing

Proposed upgrade guidelines

N/A

Submitter checklist

Give feedback

The Jira issue, if it exists, is well-described.
The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
There is automated testing or an explanation as to why this change has no tests.
New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
For dependency updates, there are links to external changelogs and, if possible, full differentials.
For new APIs and extension points, there is a link to at least one consumer.
Options

Desired reviewers

@mention

Before the changes are marked as ready-for-merge:

Maintainer checklist

Give feedback

There are at least two (2) approvals for the pull request and no outstanding requests for change.
Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
Proper changelog labels are set so that the changelog can be generated automatically.
If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).
Options

specifying the anti-aliasing implies we know better than the browser (we don't). Specifiying this globally prevents the use of sub-pixel anti-aliasing where it is available and the browsers text rendering engines are these days pretty much fantastic that they should not need these hacks. and for good measure - here is an article from 10 years ago https://usabilitypost.com/2012/11/05/stop-fixing-font-smoothing/ and the mozilla doc saying do not use it on a public facing web site. https://developer.mozilla.org/en-US/docs/Web/CSS/font-smooth

janfaracik · 2023-11-18T12:21:01Z

I was thinking of making this change myself - LGTM.

jtnord · 2023-11-30T13:41:18Z

would someone be able to check this on OS-X I only have access to linux and windows?

NotMyFault

Looks as intended on macOS.

timja

/label ready-for-merge

This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback.

Thanks!

Pesa · 2023-12-05T20:21:21Z

Looks as intended on macOS.

Just upgraded to 2.435 and text (especially bold text) looks noticeably worse for me on macOS with Chrome 120. This is with the dark-theme-plugin.

The article referenced by this commit specifically mentions light text on dark background as a special case where antialiasing may be beneficial:

Subpixel rendering gives us optimal font clarity for your typical dark text on light background. However, on Mac OS X, when this is reversed and you set light text on a dark background, you get a fairly ugly effect where the text becomes overly bold, spilling out of its lines. Switching away from subpixel rendering to antialiasing for light text on dark backgrounds makes it look lighter, countering the bolding effect.
[...]
Antialiasing is useful for certain circumstances, such as for light on dark text
[...]
Feel free to use it on light text on dark backgrounds

Note that even vanilla jenkins uses light text on dark background in some places (for the user name and "log out" in the site header).

basil · 2023-12-06T21:34:37Z

@Pesa For what it's worth, I'm extremely fussy about typography, I run Firefox on Ubuntu with a highly customized font setup (including custom fonts, anti-aliasing, RGB sub-pixel rendering, and hinting), and I use the Dark Theme, and I can't notice any issues. That isn't to deny that your problem is legitimate, but I don't see any clear evidence yet that this is a regression. If you feel strongly about this, can you please file a Jira ticket with screenshots of the old and new appearance and an explanation about why you feel the new appearance is worse? Also, don't high-traffic web sites like GitHub use the same settings as those in this PR, without user complaints?

jtnord marked this pull request as ready for review November 30, 2023 13:40

jtnord requested review from a team November 30, 2023 13:42

timja added rfe For changelog: Minor enhancement. use `major-rfe` for changes to be highlighted web-ui The PR includes WebUI changes which may need special expertise labels Nov 30, 2023

NotMyFault approved these changes Dec 4, 2023

View reviewed changes

NotMyFault requested a review from a team December 4, 2023 08:29

timja approved these changes Dec 4, 2023

View reviewed changes

comment-ops-bot bot added the ready-for-merge The PR is ready to go, and it will be merged soon if there is no negative feedback label Dec 4, 2023

NotMyFault merged commit 62d22f3 into jenkinsci:master Dec 5, 2023
16 checks passed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

do not specify anti-aliasing #8689

do not specify anti-aliasing #8689

jtnord commented Nov 10, 2023 •

edited by timja

Loading

Submitter checklist

Maintainer checklist

janfaracik commented Nov 18, 2023

jtnord commented Nov 30, 2023 •

edited

Loading

NotMyFault left a comment

timja left a comment

Pesa commented Dec 5, 2023

basil commented Dec 6, 2023

do not specify anti-aliasing #8689

do not specify anti-aliasing #8689

Conversation

jtnord commented Nov 10, 2023 • edited by timja Loading

Testing done

Proposed changelog entries

Proposed upgrade guidelines

Submitter checklist

Desired reviewers

Maintainer checklist

janfaracik commented Nov 18, 2023

jtnord commented Nov 30, 2023 • edited Loading

NotMyFault left a comment

Choose a reason for hiding this comment

timja left a comment

Choose a reason for hiding this comment

Pesa commented Dec 5, 2023

basil commented Dec 6, 2023

jtnord commented Nov 10, 2023 •

edited by timja

Loading

jtnord commented Nov 30, 2023 •

edited

Loading